Bump SQLite to 3.53.4 and fetch the wasm from GHCR via inlay - #115
Open
andreaTP wants to merge 1 commit into
Open
Bump SQLite to 3.53.4 and fetch the wasm from GHCR via inlay#115andreaTP wants to merge 1 commit into
andreaTP wants to merge 1 commit into
Conversation
The libsqlite3.wasm binary is no longer committed. It is built by wasm-lib/build.sh, published to ghcr.io/roastedroot/sqlite4j-wasm by the new Publish Wasm workflow, and pulled during generate-sources by inlay:fetch. Integrity comes from the digest pinned in wkg.lock: the registry is resolved on every build and a mismatch fails it. Signature verification is configured but left commented out in pom.xml. inlay verifies the sigstore bundle against the wasm file bytes rather than the manifest digest, so it rejects everything `cosign sign` produces; the publish workflow signs the manifest the standard way regardless, so verification can be switched on once inlay is fixed. CI no longer needs a C toolchain, so the build-wasm job and the download-artifact step are gone.
andreaTP
force-pushed
the
bump-sqlite-3.53.4
branch
from
August 24, 2026 15:06
1bd1747 to
0c777f1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The libsqlite3.wasm binary is no longer committed. It is built by wasm-lib/build.sh, published to ghcr.io/roastedroot/sqlite4j-wasm by the new Publish Wasm workflow, and pulled during generate-sources by inlay:fetch, pinned by digest in wkg.lock.
CI no longer needs a C toolchain, so the build-wasm job and the download-artifact step are gone.
Sigstore verification is configured but commented out in pom.xml: inlay verifies the bundle against the wasm file bytes, so the bundle must come from
cosign sign-blobattached as an OCI referrer rather thancosign sign, which signs the manifest digest instead. The publish workflow does it the former way; the pom config can be enabled once it has run.